docs({react,preact,solid}-query): correct inaccurate JSDoc statements - #11372

🎯 Changes

Applies to react-query, preact-query, and solid-query the same JSDoc corrections. solid-query's JSDoc was originally written by referencing react-query's, so several inaccuracies CodeRabbit caught during #11369's review turned out to be pre-existing in the react-query/preact-query source, not new mistakes introduced while porting to solid — and one further inaccuracy, caught during this PR's own review, turned out to affect all three packages including solid-query.

• mutationOptions.ts: the no-mutationKey overload's description implied a mutation becomes entirely unobservable via useMutationState without one, contradicting its own @remarks one line below (which correctly says other filters like status still work). Reworded to state the mutationKey-filter limitation directly, and trimmed the now-redundant @remarks.
• useInfiniteQuery.ts (3 overloads each): @returns listed data.pages/data.pageParams as unconditional, but they only exist while select leaves TData at its default InfiniteData<TQueryFnData> shape — a custom select can change that.
• useIsFetching.ts: "is an optional hook" misapplies "optional" to the hook itself instead of its (optional) parameters. Reworded to "The useIsFetching hook...".
• useIsMutating (inside useMutationState.ts in both packages): same "optional hook" wording fixed, plus "currently fetching" corrected to "currently pending" — core's isMutating() filters on status: 'pending', so "fetching" doesn't match what the count actually reflects.
• useMutationState.ts: the "access the latest mutation data" example filters on status: 'success', so the last returned item is the latest successful invocation, not simply the latest one (a failed or in-flight call wouldn't be in the filtered results). Reworded to say "successful" throughout that example.
• useQueries.ts (react-query, preact-query, and solid-query): claimed the per-query option objects are "identical" to useQuery's, but they aren't — the top-level subscribed option isn't accepted per query (react/preact only; solid-query has no subscribed option to begin with), and placeholderData doesn't receive information from previously rendered queries the way useQuery's does. Reworded to "mostly identical" and pointed at the existing explanation of that difference instead of asserting an equivalence that doesn't hold. (Also touches the regenerated docs/framework/solid/reference/ pages already shipped in docs(solid-query): add JSDoc and generate reference docs with TypeDoc #11369, since solid-query's useQueries.ts had the same inaccurate wording.)

✅ Checklist

• I have followed the steps in the Contributing guide.
• I have tested code changes locally with pnpm run test:pr, or these tests do not apply to this pull request.
• I fully understand the code in this pull request, including any code generated with AI assistance.

🚀 Release Impact

• This change affects published code, and I have generated a changeset.
• This change is docs/CI/dev-only (no release).

Summary by CodeRabbit

• Documentation
  • Clarified when mutations can be observed without a mutation key and how to identify the latest successful mutation results.
  • Updated infinite-query return documentation, including when data.pages and data.pageParams are available.
  • Clarified pending mutation counts and background-fetching behavior.
  • Documented differences between useQueries and useQuery, including placeholderData, and clarified top-level custom query client usage.
  • Corrected source references and refined wording across React, Preact, and Solid references.